Walkthrough

The pull request includes multiple changes across various files, primarily focusing on configuration updates, new component additions, and enhancements to existing functionalities. Key modifications involve updating environment variables, refining ESLint rules, introducing new GraphQL mutations and queries, and enhancing test coverage for several components. Additionally, there are updates to CSS styles for improved UI presentation and the addition of localization strings in multiple languages to support new features related to event management and volunteer tracking.

Changes

Possibly related PRs

• Added scripts for REACT_APP_BACKEND_WEBSOCKET_URL #2350: This PR updates the .env.example file to change the REACT_APP_BACKEND_WEBSOCKET_URL variable, which is directly related to the changes made in the main PR that also modifies this variable.
• feat: Workflow changes which will label issues automatically as per #2256 #2390: This PR introduces new translation keys related to user tag management, which may be relevant as the main PR also deals with environment variable configurations that could affect user interactions.
• fix: pull-request.yml to ignore actions on ignore-sensitive-files-pr and Introspection workflow #2391: This PR modifies the workflow to ignore certain actions, which could be indirectly related to the main PR's changes in environment variable handling and setup processes.
• Tests for newly created events #2410: This PR adds tests for newly created events, which may relate to the main PR's focus on ensuring proper configurations for event handling through environment variables.
• Upgrade @pdfme/generator to 5.0.0 #2413: This PR upgrades the @pdfme/generator package, which may be relevant as it could affect how the application handles document generation, potentially linked to the WebSocket URL changes in the main PR.
• feat: Listing the Assigned Tags on the MemberDetail screen #2425: This PR enhances the MemberDetail screen by listing assigned tags, which could relate to the main PR's focus on environment configurations that support user management features.

Poem

🐰 In the fields where bunnies play,
New paths and routes have come our way.
With webs of code and hops of cheer,
We celebrate the changes here!
From tags to events, all in a row,
Let’s jump for joy, let our progress show! 🌼

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Our Pull Request Approval Process

We have these basic policies to make the approval process smoother for our volunteer team.

Testing Your Code

Please make sure your code passes all tests. Our test code coverage system will fail if these conditions occur:

1. The overall code coverage drops below the target threshold of the repository
2. Any file in the pull request has code coverage levels below the repository threshold
3. Merge conflicts

The process helps maintain the overall reliability of the code base and is a prerequisite for getting your PR approved. Assigned reviewers regularly review the PR queue and tend to focus on PRs that are passing.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

1. comments in this PR or
2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

1. arbitrators of future discussions with other contributors about the validity of your changes
2. point of contact for evaluating the validity of your work
3. person who verifies matching issues by others that should be closed.
4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

1. PRs with issues not assigned to you will be closed by the reviewer
2. Fix the first comment in the PR so that each issue listed automatically closes

Other

1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
2. Read the CONTRIBUTING.md file make

Codecov Report

Attention: Patch coverage is 99.55291% with 3 lines in your changes missing coverage. Please review.

Project coverage is 98.26%. Comparing base (e828b78) to head (d11e850).
Report is 1 commits behind head on main.

@@            Coverage Diff             @@
##             main    #2432      +/-   ##
==========================================
+ Coverage   97.54%   98.26%   +0.71%     
==========================================
  Files         242      297      +55     
  Lines        6888     8638    +1750     
  Branches     2015     2514     +499     
==========================================
+ Hits         6719     8488    +1769     
+ Misses        157      139      -18     
+ Partials       12       11       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.